두려움을 깨진 테스트로
두려움을 깨진 테스트로.
Test-driven development is a way of managing fear during programming. I don’t mean fear in a bad way - pow widdle prwogwammew needs a pacifiew - but fear in the legitimate, “this is a hard problem and I can’t see the end from the beginning” sense. If pain is nature’s way of saying “Stop!” then fear is nature’s way of saying “Be careful.”
Being careful is good, but fear has a host of other effects:
- Fear makes you tentative.
- Fear makes you want to communicate less.
- Fear makes you shy away from feedback.
- Fear makes you grumpy.
None of these effects are helpful when programming, especially when programming something hard. So the question becomes how we face a difficult situation and,
- Instead of being tentative, begin learning concretely as quickly as possible.
- Instead of clamming up, communicate more clearly.
- Instead of avoiding feedback, search out helpful, concrete feedback.
- (You’ll have to work on grumpiness on your own.)
See also
- What not to test: 두려움이 지루함으로 바뀔 때까지 테스트를 작성하기.